Hi Horinius, Regarding the reason 1-3, I would like to know whether the users are able to view others Free/Busy information by using Outlook 2007. It is because for Outlook 2007 and Exchange 2007 users, the Outlook 2007 retrieve others Free/Busy information through Availability service URL. In addition, the OOF URL is identical to the Availability Service URL. Therefore, if we have problems with OOF, we should make sure if the Availability Service is working (or not) Regarding the Reason 4, I would like to explain that the following KB describes the issue: Error message when a user tries to set an OOF message in Outlook 2007: "Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later." http://support.microsoft.com/kb/958306/en-us The issue occurs because the AutoDiscover operation uses the SSO credentials when the user signs in to the SSO client. The AutoDiscover operation should use the credentials that are used when the user accesses a different Outlook profile. Mike

Mike. Thanks for your reply. If I'm not mistaken, Free/Busy information was introduced in Exchange 2003, right? As we've migrated from Exchange 2000 to 2007 (without passing through 2003), we have no idea what this is, and how to check if it's working. How to check it? NB: In my company, everyone's calendar is set up so that others can read one's events. This is done through "delegates".

Hi Horinius, I would like to explain that you can use following method to check whether the Free/Busy is working: 1. On the problem Outlook Client 2. Create a new meeting request 3. Add some attendee for the meeting 4. Click Schedule Assistant 5. Please check whether we are able to get other attendees Free/Busy status successfully. In addition, please check whether only the Outlook Clients which connects to Exchange through VPN encountered the problem. For example, if you have an Outlook 2007 client which connects to Exchange locally and does not join domain, please check whether the OOF issue still persists on the client. Mike

Hi Horinius,Any further updates regarding the issue? Whether we are able to check other's Free/Busy Status on the problem Client?If the Free/Busy status is correct, I would like to explain that it is a separate OOF issue. If the Free/Busy status cannot be checked, I would like to explain that the issue mostly related to Availability Service.Mike

Hi Horinius, I would like to explain that you can use following method to check whether the Free/Busy is working: 1. On the problem Outlook Client 2. Create a new meeting request 3. Add some attendee for the meeting 4. Click Schedule Assistant 5. Please check whether we are able to get other attendees Free/Busy status successfully. In addition, please check whether only the Outlook Clients which connects to Exchange through VPN encountered the problem. For example, if you have an Outlook 2007 client which connects to Exchange locally and does not join domain, please check whether the OOF issue still persists on the client. Mike Thanks for your suggestions. My co-workers confirmed me that they can't get my Free/Busy status. I got a screen-shot which shows me that: * The row representing me is hashed like this \\\\\\\\\\\ meaning "No Information" * In the "Suggested Times:" pane on the right of the window writes "Suggestions cannot be provided because free/busy data could not be retrieved." As to your second suggestion of using a non-AD-member PC, I haven't got the time to prepare one. Thanks

Hi Horinius, Thanks for your response. 1. Please let me know whether the issue occurs when Outlook 2007 client connects to Exchange locally but do not join domain 2. Please check whether we are able to get correct Availability Service URL (For Free/Busy and OOF) correctly by connecting to Autodiscover service on the problem Client. You can test the issue by using following steps: 1). on the client, launch Outlook 2). Hold down the CTRL key on your keyboard and click the Outlook icon in the notification area of the Windows taskbar, also known as the notification area. 3). In the menu that appears, click Test E-mail AutoConfiguration. 4). Enter your E-mail Address and Password (if not logged into the domain) in the respective edit boxes. 5). Choose the desired auto configuration methods with Use Autodiscover, clear other selection. 6). Click Test. Please check whether the Outlook client is able to connect to Autodiscover service to obtain Availability service URL correctly. If the Outlook is not able to connect to Autodiscover service to obtain Availability service URL, please check the log tab for more information Note: The Protocol: Exchange RPC is for internal client. The Protocol: Exchange HTTP is for Outlook Anywhere client. Mike

Hi Horinius, Please let me know the status of the issue currently. Wheter the problem client is able to connect to Autodiscover Service to retrieve Availability Service URL correctly. Mike

Last night I had tried with my own computer which isn't a domain member of my company's domain. In this computer, my Outlook also displayed the same messsage that "..... the server is currently unavailable..." However, as to Autodiscover service and Availability service URL, I'm not sure what they are and what to do.

Hi Horinius, 1. Please let me know whether your computer connects to Exchange directly or through VPN. 2. Regarding Autodiscover service and Availability Service, I would like to explain that for Outlook 2007 and Exchange 2007 environment, the Outlook 2007 configure OOF setting and retrieve other's Free/Busy informationby connecting to Availability service URL. The Outlook 2007 gather the Availability service URL by connecting to Autodiscover Service. Therefore, we firstly need to check whether the client is able to connect to Autodiscover Service to retrieve the Availability Service URL correctly. Please attempt following steps on the problem client to check whether the client is able to connect to Autodiscover service successfully: 1). On the problem Outlook client, launch Outlook 2). Hold down the CTRL key on your keyboard and click the Outlook icon in the notification area of the Windows taskbar, also known as the notification area. 3). In the menu that appears, click Test E-mail AutoConfiguration. 4). Enter your E-mail Address and Password (if not logged into the domain) in the respective edit boxes. 5). Choose the desired auto configuration methods with Use Autodiscover, clear other selection. 6). Click Test. Please check whether the Outlook client is able to connect to Autodiscover service to obtain Availability service URL correctly. If the Outlook is not able to connect to Autodiscover service to obtain Availability service URL, please check the log tab for more information Note: The Protocol: Exchange RPC is for internal client. The Protocol: Exchange HTTP is for Outlook Anywhere client. More information regarding Autodiscover and Availability Service, please refer to following articles: White Paper: Exchange 2007 Autodiscover Service http://technet.microsoft.com/en-us/library/bb332063.aspx What does Exchange 2007 Availability Service do? http://msexchangeteam.com/archive/2006/10/23/429296.aspx Mike

Hi Horinius,Any updates regarding the issue?Mike

Oh sorry Mike, I don't know why but I didn't receive alert from this thread. Thanks for your reply. Some of my computers are connected directly while some are through VPN. But the problem isn't related to VPN, because directly connected computers also have this problem. And thanks for your procedure to test Autodiscover service, esp the "log" tab which showed clearly that all methods to locate Autodiscover service fail. Then in that "White paper" article you suggested, I found this shorter and more concise article: http://support.microsoft.com/Default.aspx?kbid=940881 After reading this article, it indeed seemed to me that implementing the SRV DNS record is the simplest way to go because: * I don't have any valid SSL certificate in the Exchange server, and I don't see any interest to pay for it -- it's for internal use, not for Internet, why spend more money? * And I'm also planning to use several DNS alias to point to Exchange server, so it's quite hard to have a certificate having several names at the same time So finally, I added the _autodiscover SRV record and the problem is solved! Great! However, there's a side-effect: my users are requested to accept a certificate. Even some domain-joined computers also have to accept the certificate as if they aren't in the domain!? And my users didn't know what this certificate is and I had to explain to them. But I suppose I can't expect a more perfect solution.

hi, I am facing the same issue but only when I am connected over the VPN. I have two profiles, one that connect through LAN, and i can use outlook calendar normally. While the other profile, which connects over VPN, when i try to set-up a meeting, I am unable to see the calendar's information from others. It displays - Free busy information cannot be retrieved. Problem has started since i have upgraded to 2007 from 2003. Can you help pls?

Why ask for help? Just do what Mike Shen suggested. Or if you want the simplest solution, implement SRV record.